◀ Prev • Parts • Full • Next ▶

This section covers bridging Reticulum to other networks and protocols, transport tunnels, and developer/API tooling.

• Reticulum over DNS (Iodine transport) – Runs Reticulum over DNS using an Iodine tunnel.

• RNS over Email – Point-to-point email transport bridge using IMAP/SMTP.

• rns-tun – Reticulum TUN adapter.

• HF Nomad – Run NomadNet and Reticulum over HF radio using FreeDV.

• Reticulum over HF – Guides and resources for configuring Reticulum over HF radio.

• ReticulumHF – Encrypted HF communication using Reticulum and FreeDV.

• Modem73 – TNC frontend for the aiocdix OFDM modem.

• Reticulum RNode BLE Bridge – Creates virtual serial ports for BLE RNode devices.

Bridges connecting Reticulum specifically into the ATAK/TAK ecosystem. For general (non-TAK) situational-awareness applications, see Operate & Monitor → Situational Awareness & Coordination.

• Reticulum + ATAK + Project Tango – ATAK integration, CoT bridging, and Project Tango support.

• RNS ATAK Bridge – Bridges Reticulum peers into the TAK ecosystem.

• RTAK V2 – Android bridge between ATAK and Reticulum.

• Akita SkyEye – DroneBridge32 integration for decentralized drone telemetry and control.

• rns-mavlink – Bridges MAVLink flight controllers to QGroundControl over Reticulum.

• agronomi-fleet – Farm telemetry and actuator control using µReticulum.

• rns-signal-gateway - Bidirectional bridge between Reticulum (LXMF) and Signal via signal-cli's JSON-RPC/SSE HTTP API — text, images, files, and voice memos (including codec2 transcoding for low-bandwidth radio links).

• ANGX Bridge – General bridge between Reticulum and external communication platforms.

• Hermes for Reticulum – AI agent endpoint accessible through LXMF and Reticulum.

• Hermes + Reticulum Platform - Fail-closed Hermes policy gateway over independent Reticulum/LXMF transport.

• NomadCast – Listen to podcasts hosted on Reticulum using standard podcast apps.

• TCP KISS Server – TCP KISS server for connecting software to Reticulum.

• MeshCommander – Hardware-agnostic TUI and bridge for handhelds and LoRa modules.

• RNS Over MeshCore - Interface for Reticulum Network Stack (RNS) using MeshCore as the underlying networking layer to utilize existing LoRa/mesh hardware.

• rns-gateway – Reticulum gateway that runs inside MeshCore firmware on a Heltec WiFi LoRa 32 V4. Embeds microReticulum, exposes a TCP server for RNS clients (MeshChat, Sideband, etc.), and uses a private MeshCore channel as long-haul transport between sites.

• Reticulum Meshtastic Integration – Forwards Meshtastic packets into the Reticulum Community Hub (RCH).

• Reticulum - Meshtastic Interface - This fork aims to preserve Reticulum compatibility and ease of use while maintaining selected integrations. It currently adds a native MeshtasticInterface for transporting Reticulum traffic over Meshtastic radios. The interface uses Meshtastic port number 76 and includes bounded binary fragmentation, sender-separated reassembly, configurable channel and modem settings, conservative airtime safeguards, and radio reconnect handling.

• RNS Meshtastic Interface Python File - A standalone Reticulum interface for transporting binary RNS traffic over Meshtastic radios. The interface uses Meshtastic's reserved RETICULUM_TUNNEL_APP application port (port 76). It provides bounded binary fragmentation, sender-isolated reassembly, CRC validation, configurable channel and modem settings, paced transmission, and automatic reconnect handling.

• BATMAN-adv + Reticulum integration – Runs Reticulum as a secure overlay on top of BATMAN-adv Layer 2 mesh networking.

◀ Prev • Parts • Full • Next ▶